Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c23afa93035ab9eb85f3411366e008343170c2ae2276528a96aeef16d0149de

Tx prefix hash: c72e5a6fe6fe89a460cb853e3ac71c00d697ba4bb09e3524a360f0b3c58d091d
Tx public key: bfd6cead7e0ff3b60633debb2d65c02d52a9660c87a41f54e179107959413691
Timestamp: 1702616239 Timestamp [UCT]: 2023-12-15 04:57:19 Age [y:d:h:m:s]: 01:036:15:37:54
Block: 913428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287522 RingCT/type: yes/0
Extra: 01bfd6cead7e0ff3b60633debb2d65c02d52a9660c87a41f54e17910795941369102110000000b33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d1fd9a43fb37a7eab1d735578fefe8003ea7f4ca8c4baadd7c05b4afe9c6a1c 0.600000000000 1370696 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": 913438, "vin": [ { "gen": { "height": 913428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d1fd9a43fb37a7eab1d735578fefe8003ea7f4ca8c4baadd7c05b4afe9c6a1c" } } ], "extra": [ 1, 191, 214, 206, 173, 126, 15, 243, 182, 6, 51, 222, 187, 45, 101, 192, 45, 82, 169, 102, 12, 135, 164, 31, 84, 225, 121, 16, 121, 89, 65, 54, 145, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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