Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c02aacf1988a1b227266a1321fa650ccec14d76714f1355cec0f65ecef19cd8

Tx prefix hash: 3c08bdf1d6e3acfc93b616ec0203aac2862f3f0cd03e3b668604b24d118be9d6
Tx public key: ad2f29c1474c97a43090f7194976814b6d624c95cd782063ce2b2ad5b6d94f4e
Timestamp: 1702137407 Timestamp [UCT]: 2023-12-09 15:56:47 Age [y:d:h:m:s]: 01:038:07:52:16
Block: 909470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288749 RingCT/type: yes/0
Extra: 01ad2f29c1474c97a43090f7194976814b6d624c95cd782063ce2b2ad5b6d94f4e0211000000044b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a787c2337fbcd3d69f90e1ce85b2f9807b546e213f1c9df347ae52e12bbc2b43 0.600000000000 1366559 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": 909480, "vin": [ { "gen": { "height": 909470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a787c2337fbcd3d69f90e1ce85b2f9807b546e213f1c9df347ae52e12bbc2b43" } } ], "extra": [ 1, 173, 47, 41, 193, 71, 76, 151, 164, 48, 144, 247, 25, 73, 118, 129, 75, 109, 98, 76, 149, 205, 120, 32, 99, 206, 43, 42, 213, 182, 217, 79, 78, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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