Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f90e5b596b6d44cf21c62c4fdc1bcc2dd2b3812f4a7dd1c645526da2173d021

Tx prefix hash: 92e82296f31c784ed77bc1493c2c432b2a709d06d848ba5219b11ad78a81d31b
Tx public key: bf54f4b1b7f56b9bddd42177ce122efd430436c72e93770e10022e8829496ed3
Timestamp: 1731847285 Timestamp [UCT]: 2024-11-17 12:41:25 Age [y:d:h:m:s]: 00:325:20:05:17
Block: 1155674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230372 RingCT/type: yes/0
Extra: 01bf54f4b1b7f56b9bddd42177ce122efd430436c72e93770e10022e8829496ed3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c3e3abbe0e92b7ee24187dc87ee5a6a95f9e32c0c3a5af1dd57b3121e4ae14 0.600000000000 1641291 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": 1155684, "vin": [ { "gen": { "height": 1155674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c3e3abbe0e92b7ee24187dc87ee5a6a95f9e32c0c3a5af1dd57b3121e4ae14" } } ], "extra": [ 1, 191, 84, 244, 177, 183, 245, 107, 155, 221, 212, 33, 119, 206, 18, 46, 253, 67, 4, 54, 199, 46, 147, 119, 14, 16, 2, 46, 136, 41, 73, 110, 211, 2, 17, 0, 0, 0, 5, 0, 127, 151, 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