Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9a4e75c658805baf2a4971c11ee0616ae20489c02a69dc71b6bb581e5e4368a

Tx prefix hash: ab1a8230a4948bfd37483e1c80d5f3cc0560dd3da0e25d0b3769aa7274434911
Tx public key: e8d27c578096bd208fb4bbe77caca997d95b8ffec9a7c6cfed435cf7c0e9a414
Timestamp: 1737497082 Timestamp [UCT]: 2025-01-21 22:04:42 Age [y:d:h:m:s]: 00:153:08:00:39
Block: 1202412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109216 RingCT/type: yes/0
Extra: 01e8d27c578096bd208fb4bbe77caca997d95b8ffec9a7c6cfed435cf7c0e9a414021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a46a6bab4efaa76f188439b60596c71b070d8b600c7459b5f9539ba5b6b0c3fd 0.600000000000 1689075 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": 1202422, "vin": [ { "gen": { "height": 1202412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a46a6bab4efaa76f188439b60596c71b070d8b600c7459b5f9539ba5b6b0c3fd" } } ], "extra": [ 1, 232, 210, 124, 87, 128, 150, 189, 32, 143, 180, 187, 231, 124, 172, 169, 151, 217, 91, 143, 254, 201, 167, 198, 207, 237, 67, 92, 247, 192, 233, 164, 20, 2, 17, 0, 0, 0, 6, 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