Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f9d95c3132961241743795833f2f6592cee8b234652b9c1b2a2cec9a26bf39d

Tx prefix hash: 486f915d52b571f0c47cef723694bf1bcda190029cff81f9dc4c7a5b7126ad29
Tx public key: af594e2dae2c943d7cfa3402e2e48e5a0b37c8f7a0d321ea34e03cc54cbc8d9a
Timestamp: 1739642253 Timestamp [UCT]: 2025-02-15 17:57:33 Age [y:d:h:m:s]: 00:271:16:48:49
Block: 1219915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191978 RingCT/type: yes/0
Extra: 01af594e2dae2c943d7cfa3402e2e48e5a0b37c8f7a0d321ea34e03cc54cbc8d9a0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6971ab699eb367447eac53e942bbe451bbcc81d327a1fda084834ba27f2edf8 0.600000000000 1706750 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": 1219925, "vin": [ { "gen": { "height": 1219915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6971ab699eb367447eac53e942bbe451bbcc81d327a1fda084834ba27f2edf8" } } ], "extra": [ 1, 175, 89, 78, 45, 174, 44, 148, 61, 124, 250, 52, 2, 226, 228, 142, 90, 11, 55, 200, 247, 160, 211, 33, 234, 52, 224, 60, 197, 76, 188, 141, 154, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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