Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93806fde28e965ec4d0e00b8a988a2a55bec5252c2a0b571becc700cedc955a3

Tx prefix hash: cf270e7049b22025affdfb5780d03d7239527f1e76f7329833193bfa343598bc
Tx public key: ff361dc46a0a5fa627c0938de34995db083d001c7a717315a78a9531a0863f96
Timestamp: 1634782609 Timestamp [UCT]: 2021-10-21 02:16:49 Age [y:d:h:m:s]: 03:031:00:18:34
Block: 357142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 800386 RingCT/type: yes/0
Extra: 01ff361dc46a0a5fa627c0938de34995db083d001c7a717315a78a9531a0863f9602110000000efdc024ec000000000000000000

1 output(s) for total of 40.238400639000 dcy

stealth address amount amount idx
00: b71e13a4923a6050e00325fbbefcb85b6a4837e7eba50ea374d0b5a66f35a9c3 40.238400639000 728370 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": 357152, "vin": [ { "gen": { "height": 357142 } } ], "vout": [ { "amount": 40238400639, "target": { "key": "b71e13a4923a6050e00325fbbefcb85b6a4837e7eba50ea374d0b5a66f35a9c3" } } ], "extra": [ 1, 255, 54, 29, 196, 106, 10, 95, 166, 39, 192, 147, 141, 227, 73, 149, 219, 8, 61, 0, 28, 122, 113, 115, 21, 167, 138, 149, 49, 160, 134, 63, 150, 2, 17, 0, 0, 0, 14, 253, 192, 36, 236, 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