Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0547ec46a519fdc72f29ad5f8a61a275876bb17bb165991c9945598901f63890

Tx prefix hash: 742dc4e7d3036a0883f799f67d6e2c6b6a33efc9f413532fefa66a5dd67db0bd
Tx public key: 64a3d5a676f42094375e5e13bdf3a529205c853abd57b5058739921b7c8d34b2
Timestamp: 1681605634 Timestamp [UCT]: 2023-04-16 00:40:34 Age [y:d:h:m:s]: 01:213:07:58:21
Block: 739485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413923 RingCT/type: yes/0
Extra: 0164a3d5a676f42094375e5e13bdf3a529205c853abd57b5058739921b7c8d34b20211000000015029cbac000000000000000000

1 output(s) for total of 2.176604079000 dcy

stealth address amount amount idx
00: 7f181b4da230c19b0195e23db48cc3c9471d44b57ee6d349266eb5af66d2d668 2.176604079000 1186338 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": 739495, "vin": [ { "gen": { "height": 739485 } } ], "vout": [ { "amount": 2176604079, "target": { "key": "7f181b4da230c19b0195e23db48cc3c9471d44b57ee6d349266eb5af66d2d668" } } ], "extra": [ 1, 100, 163, 213, 166, 118, 244, 32, 148, 55, 94, 94, 19, 189, 243, 165, 41, 32, 92, 133, 58, 189, 87, 181, 5, 135, 57, 146, 27, 124, 141, 52, 178, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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