Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a2dfa41c17634a4ff44960deb157fe380184d4fe332cd909c2bda68348de664

Tx prefix hash: c77a5e36f5455bc7e597970f5d33be9b401f3f81cae13af28b41fcd904470b2e
Tx public key: 0aa4ade94492b497ae2c3b161235e1e09df6acd1d0aefee7169119a241b2dc97
Timestamp: 1734815738 Timestamp [UCT]: 2024-12-21 21:15:38 Age [y:d:h:m:s]: 00:178:18:49:46
Block: 1180301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127460 RingCT/type: yes/0
Extra: 010aa4ade94492b497ae2c3b161235e1e09df6acd1d0aefee7169119a241b2dc97021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de168f6921b26e294f0c598b7935d02950c5047a28c9c532e9e983a74c001552 0.600000000000 1666712 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": 1180311, "vin": [ { "gen": { "height": 1180301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de168f6921b26e294f0c598b7935d02950c5047a28c9c532e9e983a74c001552" } } ], "extra": [ 1, 10, 164, 173, 233, 68, 146, 180, 151, 174, 44, 59, 22, 18, 53, 225, 224, 157, 246, 172, 209, 208, 174, 254, 231, 22, 145, 25, 162, 65, 178, 220, 151, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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