Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 14c3f94a4533d0ce1329b0b5faf26f5148ed7ebd2aa03cf9b3a47253751edf89

Tx prefix hash: 297fd07f3dc6b41f21633641020dfae4ee37d9583dd4ebab87e13978eafe0d5a
Tx public key: ba21dbd2d3f53db152d77204f2f7bf7813028522c6902e6bccf7a45e11af77b6
Timestamp: 1719550898 Timestamp [UCT]: 2024-06-28 05:01:38 Age [y:d:h:m:s]: 00:293:06:24:01
Block: 1053828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209557 RingCT/type: yes/0
Extra: 01ba21dbd2d3f53db152d77204f2f7bf7813028522c6902e6bccf7a45e11af77b602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18bc2e240f527bcac5e6f113c5e2d85c11fee579d919b951d56c2df3ff813c2f 0.600000000000 1524179 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1053838, "vin": [ { "gen": { "height": 1053828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18bc2e240f527bcac5e6f113c5e2d85c11fee579d919b951d56c2df3ff813c2f" } } ], "extra": [ 1, 186, 33, 219, 210, 211, 245, 61, 177, 82, 215, 114, 4, 242, 247, 191, 120, 19, 2, 133, 34, 198, 144, 46, 107, 204, 247, 164, 94, 17, 175, 119, 182, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8