Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b032493d53d8d7f3754a82c562d28ce1b11ef94dc428bda0395e81ef8e05b01

Tx prefix hash: 4924bf5f4f2de145246f74e7fbfc468d4ef19c4689c2768a5f467a75d1fa829d
Tx public key: e6de0386c8a0c36db1c5c87791bce4e6a40b69b535b06aa20130b3fa396c02fe
Timestamp: 1724844489 Timestamp [UCT]: 2024-08-28 11:28:09 Age [y:d:h:m:s]: 00:244:04:53:39
Block: 1097718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174411 RingCT/type: yes/0
Extra: 01e6de0386c8a0c36db1c5c87791bce4e6a40b69b535b06aa20130b3fa396c02fe021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a04f7905700c31e2f70556c0b2cc4bb35ed38e6fd3cbfc9158f9560a616368c9 0.600000000000 1573183 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": 1097728, "vin": [ { "gen": { "height": 1097718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a04f7905700c31e2f70556c0b2cc4bb35ed38e6fd3cbfc9158f9560a616368c9" } } ], "extra": [ 1, 230, 222, 3, 134, 200, 160, 195, 109, 177, 197, 200, 119, 145, 188, 228, 230, 164, 11, 105, 181, 53, 176, 106, 162, 1, 48, 179, 250, 57, 108, 2, 254, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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