Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 880aaa6739b4cc2f21a170705e33823ddb440668afe81ca8e0a23da8382c4cc4

Tx prefix hash: b01b7f55acff23a21ed3fda9a567db6dfd71f84cd96062a4ea640d7a4e426a97
Tx public key: 0c2185fe67e17612bddfbb21f1e3363094e6c04053de9ceb1677ce004087c66d
Timestamp: 1699001234 Timestamp [UCT]: 2023-11-03 08:47:14 Age [y:d:h:m:s]: 01:215:12:44:00
Block: 883673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415076 RingCT/type: yes/0
Extra: 010c2185fe67e17612bddfbb21f1e3363094e6c04053de9ceb1677ce004087c66d02110000000333af99f4000000000000000000

1 output(s) for total of 0.724476876000 dcy

stealth address amount amount idx
00: ec9b5d02213d6d7c9f91ef7abf0ac635766f84f9a6aa33bc200ff6f40e82e196 0.724476876000 1339377 of 0

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": 883683, "vin": [ { "gen": { "height": 883673 } } ], "vout": [ { "amount": 724476876, "target": { "key": "ec9b5d02213d6d7c9f91ef7abf0ac635766f84f9a6aa33bc200ff6f40e82e196" } } ], "extra": [ 1, 12, 33, 133, 254, 103, 225, 118, 18, 189, 223, 187, 33, 241, 227, 54, 48, 148, 230, 192, 64, 83, 222, 156, 235, 22, 119, 206, 0, 64, 135, 198, 109, 2, 17, 0, 0, 0, 3, 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