Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b54cba201406d156cb20322bab2ea45d742ddcc0a0a87f79e4b2f87e6529e84

Tx prefix hash: 2f58aa4a81dd4336daac9e9c3bedbd16244376ea9a9ddea1d9a371f1865b0de0
Tx public key: 71741323a1c0b44fe76c759d02bdeafd789e67c974734a7760bd3d1d0d49d6ea
Timestamp: 1686462791 Timestamp [UCT]: 2023-06-11 05:53:11 Age [y:d:h:m:s]: 02:176:19:01:39
Block: 779778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646139 RingCT/type: yes/0
Extra: 0171741323a1c0b44fe76c759d02bdeafd789e67c974734a7760bd3d1d0d49d6ea02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.600599945000 dcy

stealth address amount amount idx
00: adac1f2d7c0c4d3a31f9f3705cbfca3b38965367ae9c50d22bdf9653af843ff8 1.600599945000 1229453 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": 779788, "vin": [ { "gen": { "height": 779778 } } ], "vout": [ { "amount": 1600599945, "target": { "key": "adac1f2d7c0c4d3a31f9f3705cbfca3b38965367ae9c50d22bdf9653af843ff8" } } ], "extra": [ 1, 113, 116, 19, 35, 161, 192, 180, 79, 231, 108, 117, 157, 2, 189, 234, 253, 120, 158, 103, 201, 116, 115, 74, 119, 96, 189, 61, 29, 13, 73, 214, 234, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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