Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b245d232925f65bf1d47409f643f4019d63974e8ba6776b17f8eefd94c7a5712

Tx prefix hash: 8204bbd0660ed6de7a9e7cfaea741e06aad0d6933f3826b23608e568bb708637
Tx public key: 643f939ae95e001d43586bb7464e4595db4f9245e485a1432235117e734d847c
Timestamp: 1700821299 Timestamp [UCT]: 2023-11-24 10:21:39 Age [y:d:h:m:s]: 01:132:05:51:57
Block: 898552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355685 RingCT/type: yes/0
Extra: 01643f939ae95e001d43586bb7464e4595db4f9245e485a1432235117e734d847c021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.646731781000 dcy

stealth address amount amount idx
00: e2a5828aca8fee0d4bb4a15e4a0bf24f1f723c3c1066f2c1ce5546d89485ac02 0.646731781000 1354973 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": 898562, "vin": [ { "gen": { "height": 898552 } } ], "vout": [ { "amount": 646731781, "target": { "key": "e2a5828aca8fee0d4bb4a15e4a0bf24f1f723c3c1066f2c1ce5546d89485ac02" } } ], "extra": [ 1, 100, 63, 147, 154, 233, 94, 0, 29, 67, 88, 107, 183, 70, 78, 69, 149, 219, 79, 146, 69, 228, 133, 161, 67, 34, 53, 17, 126, 115, 77, 132, 124, 2, 17, 0, 0, 0, 1, 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