Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02fcea99c2360bc1a186539bb9a86023678e52b370682fab98075b7b901cce0a

Tx prefix hash: 78b860c145d307db2614bb24b87bd75f2c421a40042bc7dabb253141f5627a6f
Tx public key: 38bc82bd7c15d14a3fd9b00381c443e6ba2f08f131583bf65b7d54aa98f8860b
Timestamp: 1732892292 Timestamp [UCT]: 2024-11-29 14:58:12 Age [y:d:h:m:s]: 00:122:10:29:20
Block: 1164345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87299 RingCT/type: yes/0
Extra: 0138bc82bd7c15d14a3fd9b00381c443e6ba2f08f131583bf65b7d54aa98f8860b02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47104b9ef0c21a86bc90052be49fb4a41c75e167ee0e410b7b0f9d0f9792d7c2 0.600000000000 1650018 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": 1164355, "vin": [ { "gen": { "height": 1164345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47104b9ef0c21a86bc90052be49fb4a41c75e167ee0e410b7b0f9d0f9792d7c2" } } ], "extra": [ 1, 56, 188, 130, 189, 124, 21, 209, 74, 63, 217, 176, 3, 129, 196, 67, 230, 186, 47, 8, 241, 49, 88, 59, 246, 91, 125, 84, 170, 152, 248, 134, 11, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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