Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb8bcdb02413f4471c93bccb8cf0c7c24206f616cb77a78207763cde5d103a22

Tx prefix hash: 7c6f019a580bcf5c0b535309b6707ee790bef0be2566cb6d45695a4271dfef81
Tx public key: e8c410136bf402a208d4494a0867a9ba9cdb393dcafd9231788baa95d1c08096
Timestamp: 1717968288 Timestamp [UCT]: 2024-06-09 21:24:48 Age [y:d:h:m:s]: 00:278:18:29:40
Block: 1040707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199235 RingCT/type: yes/0
Extra: 01e8c410136bf402a208d4494a0867a9ba9cdb393dcafd9231788baa95d1c08096021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ed3c7d9f245019d3b007e27da98760c7320921b0aa74cba115dbad26150f2cb 0.600000000000 1509366 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": 1040717, "vin": [ { "gen": { "height": 1040707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ed3c7d9f245019d3b007e27da98760c7320921b0aa74cba115dbad26150f2cb" } } ], "extra": [ 1, 232, 196, 16, 19, 107, 244, 2, 162, 8, 212, 73, 74, 8, 103, 169, 186, 156, 219, 57, 61, 202, 253, 146, 49, 120, 139, 170, 149, 209, 192, 128, 150, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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