Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bc8eb6ba54b8d788b6c886f0698b722c815dd074066cbe4217c2f5fbf9741a0

Tx prefix hash: 7e6c06add60623cbe75d1c8c97e48c18d314dc6bbe0d4f98ed3697e6b6f0fd6e
Tx public key: 836ab7e189c0ed0da6b8051c8e28478a4a4dd5cb6013a185b7ae37737f00d446
Timestamp: 1698599024 Timestamp [UCT]: 2023-10-29 17:03:44 Age [y:d:h:m:s]: 01:162:07:39:50
Block: 880345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377001 RingCT/type: yes/0
Extra: 01836ab7e189c0ed0da6b8051c8e28478a4a4dd5cb6013a185b7ae37737f00d446021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.743107387000 dcy

stealth address amount amount idx
00: 12f2261697a426a0c3c53bae10d4d8ced38f4ea229af8c780670e48a074ea8a7 0.743107387000 1335901 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": 880355, "vin": [ { "gen": { "height": 880345 } } ], "vout": [ { "amount": 743107387, "target": { "key": "12f2261697a426a0c3c53bae10d4d8ced38f4ea229af8c780670e48a074ea8a7" } } ], "extra": [ 1, 131, 106, 183, 225, 137, 192, 237, 13, 166, 184, 5, 28, 142, 40, 71, 138, 74, 77, 213, 203, 96, 19, 161, 133, 183, 174, 55, 115, 127, 0, 212, 70, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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