Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b28c5326f399b8681769dc1e4b0829d4d0936ddd80e2dc3c10d8686ad7be894

Tx prefix hash: a990d3efef694031a83e6e5ba22942345ebd5cd8da0031227066f460ea1fc4c1
Tx public key: 7ca9165a12a1af39ca0efd58c6b3ac63493438e90c73cf2618f5f39e6073ac9b
Timestamp: 1754392494 Timestamp [UCT]: 2025-08-05 11:14:54 Age [y:d:h:m:s]: 00:012:07:18:16
Block: 1340747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7926 RingCT/type: yes/0
Extra: 017ca9165a12a1af39ca0efd58c6b3ac63493438e90c73cf2618f5f39e6073ac9b02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 989e89ce09e228e8c1f33b73ad709a4c5e3948525e991f9b5c72d691368f20c9 0.600000000000 1828566 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": 1340757, "vin": [ { "gen": { "height": 1340747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "989e89ce09e228e8c1f33b73ad709a4c5e3948525e991f9b5c72d691368f20c9" } } ], "extra": [ 1, 124, 169, 22, 90, 18, 161, 175, 57, 202, 14, 253, 88, 198, 179, 172, 99, 73, 52, 56, 233, 12, 115, 207, 38, 24, 245, 243, 158, 96, 115, 172, 155, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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