Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 818ff9fe217de80e1b6555982d82f39f7144f63b9c7fad8fe99d0b8aedd1c2c8

Tx prefix hash: 6896e92c1e095031ff9eed190adfd0e9a52f3590073d32abe4af27b526f0ce05
Tx public key: 8bc0d2ae7a762dfd5ff28d8e629b3725d6d21099d43e2687c51ea98eddb32671
Timestamp: 1757777753 Timestamp [UCT]: 2025-09-13 15:35:53 Age [y:d:h:m:s]: 00:117:16:51:00
Block: 1367641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84287 RingCT/type: yes/0
Extra: 018bc0d2ae7a762dfd5ff28d8e629b3725d6d21099d43e2687c51ea98eddb32671021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f2126aba5aa51ad9e3657d0a644e404d0e0e89c7b9008ec5e8ae8b8c16b4223 0.600000000000 1855680 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": 1367651, "vin": [ { "gen": { "height": 1367641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f2126aba5aa51ad9e3657d0a644e404d0e0e89c7b9008ec5e8ae8b8c16b4223" } } ], "extra": [ 1, 139, 192, 210, 174, 122, 118, 45, 253, 95, 242, 141, 142, 98, 155, 55, 37, 214, 210, 16, 153, 212, 62, 38, 135, 197, 30, 169, 142, 221, 179, 38, 113, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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