Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15aacf8666288cabc08f9e89665f26427674b3759c8d8146b0a6044bb813ee26

Tx prefix hash: 27deb2c36eb7fd31709781d0bdb2e41a5b7bf86378f67299df23ec302a250c65
Tx public key: 5f41c71a1a171df6ee936653d6e7c28aa30b8135a4c3f388c3a4483924b92852
Timestamp: 1733980031 Timestamp [UCT]: 2024-12-12 05:07:11 Age [y:d:h:m:s]: 00:108:02:57:45
Block: 1173364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77046 RingCT/type: yes/0
Extra: 015f41c71a1a171df6ee936653d6e7c28aa30b8135a4c3f388c3a4483924b92852021100000002a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4052250ee659dc4511547f5781d519c0aeb5d96413603382b53c95a4a2d34e0 0.600000000000 1659379 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": 1173374, "vin": [ { "gen": { "height": 1173364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4052250ee659dc4511547f5781d519c0aeb5d96413603382b53c95a4a2d34e0" } } ], "extra": [ 1, 95, 65, 199, 26, 26, 23, 29, 246, 238, 147, 102, 83, 214, 231, 194, 138, 163, 11, 129, 53, 164, 195, 243, 136, 195, 164, 72, 57, 36, 185, 40, 82, 2, 17, 0, 0, 0, 2, 162, 215, 95, 68, 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