Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae000f0e0cca9c9aefdfe9044819b29a2f2ac2ed361cb45b406b074da81f4601

Tx prefix hash: 56b3554346547b59b5483a3c3174aa805c1622aba84790fd0b6b9f967e911b1e
Tx public key: 2691278a0b00339966b953dc761a5db802b3347a0c4cf8693df51d4ee8e4f551
Timestamp: 1743321605 Timestamp [UCT]: 2025-03-30 08:00:05 Age [y:d:h:m:s]: 00:235:06:29:42
Block: 1250409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165879 RingCT/type: yes/0
Extra: 012691278a0b00339966b953dc761a5db802b3347a0c4cf8693df51d4ee8e4f5510211000000069ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fddc62680860b2606cdb551e631f2fa0f31851d28035bf9f068be1ef2f49f51 0.600000000000 1737458 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": 1250419, "vin": [ { "gen": { "height": 1250409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fddc62680860b2606cdb551e631f2fa0f31851d28035bf9f068be1ef2f49f51" } } ], "extra": [ 1, 38, 145, 39, 138, 11, 0, 51, 153, 102, 185, 83, 220, 118, 26, 93, 184, 2, 179, 52, 122, 12, 76, 248, 105, 61, 245, 29, 78, 232, 228, 245, 81, 2, 17, 0, 0, 0, 6, 155, 166, 41, 223, 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