Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12e2cd4651d80ab3178c39974275d3fbff9fbd13902dc18011237890c4363fa2

Tx prefix hash: fdbbe9871311332e9311c71b191ebec5f5ae4f531d6dbee4af3eb7da73df2038
Tx public key: a7c31ab8ee80ef29f13d4139bb292b4db0bac717fbef9443757e1ca78a5987bb
Timestamp: 1704894276 Timestamp [UCT]: 2024-01-10 13:44:36 Age [y:d:h:m:s]: 01:076:00:05:07
Block: 932313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315409 RingCT/type: yes/0
Extra: 01a7c31ab8ee80ef29f13d4139bb292b4db0bac717fbef9443757e1ca78a5987bb02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d417d5073545ca07db8f283aa87e3d3fb8d89e652c259d05a8656c51508aaf1b 0.600000000000 1390245 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": 932323, "vin": [ { "gen": { "height": 932313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d417d5073545ca07db8f283aa87e3d3fb8d89e652c259d05a8656c51508aaf1b" } } ], "extra": [ 1, 167, 195, 26, 184, 238, 128, 239, 41, 241, 61, 65, 57, 187, 41, 43, 77, 176, 186, 199, 23, 251, 239, 148, 67, 117, 126, 28, 167, 138, 89, 135, 187, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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