Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 436379555ec1d9e6865b65604fd00e2e8727022006531256428dd24b3fb3b19d

Tx prefix hash: ff283f87611aa12bd57fb6f0a07547ebdd026fd885299779f28b399f6874e858
Tx public key: 17e60d8fe87e06a445287eadeae12fd1f51d25d294a49c6eecc0336bf12192dd
Timestamp: 1717318584 Timestamp [UCT]: 2024-06-02 08:56:24 Age [y:d:h:m:s]: 00:293:07:23:46
Block: 1035336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209615 RingCT/type: yes/0
Extra: 0117e60d8fe87e06a445287eadeae12fd1f51d25d294a49c6eecc0336bf12192dd0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53df0b31f4e8d627d5d208fb3f28e7d35a2f1fc92f95201a4bc55b3811edb99b 0.600000000000 1503857 of 15

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": 1035346, "vin": [ { "gen": { "height": 1035336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53df0b31f4e8d627d5d208fb3f28e7d35a2f1fc92f95201a4bc55b3811edb99b" } } ], "extra": [ 1, 23, 230, 13, 143, 232, 126, 6, 164, 69, 40, 126, 173, 234, 225, 47, 209, 245, 29, 37, 210, 148, 164, 156, 110, 236, 192, 51, 107, 241, 33, 146, 221, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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