Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f57d3a4b5a03cf32fa2d8ee7d31dacf5327533f8e2ef797f7416c9e44ddd099a

Tx prefix hash: 38911fdf3e4585d88dc5aa08d6877552de30537866a82864e3160a1e9aad5ab7
Tx public key: ffc2c50d1832e092665e8ee33f24630680653e67592c2b41041bcf2d77254426
Timestamp: 1707028437 Timestamp [UCT]: 2024-02-04 06:33:57 Age [y:d:h:m:s]: 01:086:09:55:08
Block: 949999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322832 RingCT/type: yes/0
Extra: 01ffc2c50d1832e092665e8ee33f24630680653e67592c2b41041bcf2d7725442602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f410db3ef253e0075475298029c985897aa9e4c3f7d4f2244d2cfc215b802585 0.600000000000 1408539 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": 950009, "vin": [ { "gen": { "height": 949999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f410db3ef253e0075475298029c985897aa9e4c3f7d4f2244d2cfc215b802585" } } ], "extra": [ 1, 255, 194, 197, 13, 24, 50, 224, 146, 102, 94, 142, 227, 63, 36, 99, 6, 128, 101, 62, 103, 89, 44, 43, 65, 4, 27, 207, 45, 119, 37, 68, 38, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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