Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e97ff65b24b1f1883ffa51dbd78c625a695641166f9b4c628d397d613a34ccd

Tx prefix hash: a1da34e71d98dabaaf75f9d7433b5ff03fac28582533412b7b26b5aed1a7b73d
Tx public key: bac9103eb0f9470a25e6d8b5080d9a543047989fbd820efde60e8fdec378275b
Timestamp: 1592760660 Timestamp [UCT]: 2020-06-21 17:31:00 Age [y:d:h:m:s]: 04:147:10:44:05
Block: 110089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043904 RingCT/type: yes/0
Extra: 01bac9103eb0f9470a25e6d8b5080d9a543047989fbd820efde60e8fdec378275b0211000000413667f28a000000000000000000

1 output(s) for total of 264.990430553000 dcy

stealth address amount amount idx
00: 395b9f9490d5100000e8a542f838b48d6382e1d5a0b77e39b0534fb2a28eb8dc 264.990430553000 190713 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": 110099, "vin": [ { "gen": { "height": 110089 } } ], "vout": [ { "amount": 264990430553, "target": { "key": "395b9f9490d5100000e8a542f838b48d6382e1d5a0b77e39b0534fb2a28eb8dc" } } ], "extra": [ 1, 186, 201, 16, 62, 176, 249, 71, 10, 37, 230, 216, 181, 8, 13, 154, 84, 48, 71, 152, 159, 189, 130, 14, 253, 230, 14, 143, 222, 195, 120, 39, 91, 2, 17, 0, 0, 0, 65, 54, 103, 242, 138, 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