Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 888a85ec51b25c037b1f6fd86edf13d43bddfa9a27c8fe5f6b81ea311e0e3d9e

Tx prefix hash: 7e29470d49bfaf826ede595cdb3ab52f32b93009820ccaa48cf5cb0bd11ec360
Tx public key: 48e36235aad8c221e6d268d8c4f370540d89440e0af9c2815c0f9326406bb0e4
Timestamp: 1669056316 Timestamp [UCT]: 2022-11-21 18:45:16 Age [y:d:h:m:s]: 02:097:11:37:41
Block: 636112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591353 RingCT/type: yes/0
Extra: 0148e36235aad8c221e6d268d8c4f370540d89440e0af9c2815c0f9326406bb0e402110000000874b6d784000000000000000000

1 output(s) for total of 4.789574007000 dcy

stealth address amount amount idx
00: 7066d4ab8510e8e2ab404c6f8b95f64f14fef425943faab27b6aae9ec0e0cefd 4.789574007000 1075501 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": 636122, "vin": [ { "gen": { "height": 636112 } } ], "vout": [ { "amount": 4789574007, "target": { "key": "7066d4ab8510e8e2ab404c6f8b95f64f14fef425943faab27b6aae9ec0e0cefd" } } ], "extra": [ 1, 72, 227, 98, 53, 170, 216, 194, 33, 230, 210, 104, 216, 196, 243, 112, 84, 13, 137, 68, 14, 10, 249, 194, 129, 92, 15, 147, 38, 64, 107, 176, 228, 2, 17, 0, 0, 0, 8, 116, 182, 215, 132, 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