Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bd1b72d1242072f4668c49e342b4b4397e3f9875e842b99f47e2b91b0853c80

Tx prefix hash: 659d63f7d838551e35343e1ffd6beeee55f44e43125378f16a9bfb1610a3cbaa
Tx public key: d4bf7a44316fe3f4844ce5e18c06b0c0fb92eef82d4ffb950ebfe69ac429417c
Timestamp: 1730499022 Timestamp [UCT]: 2024-11-01 22:10:22 Age [y:d:h:m:s]: 00:081:14:50:17
Block: 1144509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58362 RingCT/type: yes/0
Extra: 01d4bf7a44316fe3f4844ce5e18c06b0c0fb92eef82d4ffb950ebfe69ac429417c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f78a06e8708772621059d60ee6089705009df151a1e2bc3c5cafceb04b95f3c4 0.600000000000 1628744 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": 1144519, "vin": [ { "gen": { "height": 1144509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f78a06e8708772621059d60ee6089705009df151a1e2bc3c5cafceb04b95f3c4" } } ], "extra": [ 1, 212, 191, 122, 68, 49, 111, 227, 244, 132, 76, 229, 225, 140, 6, 176, 192, 251, 146, 238, 248, 45, 79, 251, 149, 14, 191, 230, 154, 196, 41, 65, 124, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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