Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e434e3904de29a027cd6d7e277876d9d1a136c4ec0bc335fdacac081b1853d06

Tx prefix hash: b2c0136573791982272b60d8bdcc12963f9d0d2b809aa123e70e66806dddf7a6
Tx public key: 5121e92dae7a9ad808aa24c6f2a0bb6c9ab033cc7adf331b97e081e6e2df3e1a
Timestamp: 1733905201 Timestamp [UCT]: 2024-12-11 08:20:01 Age [y:d:h:m:s]: 00:101:06:31:24
Block: 1172735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72170 RingCT/type: yes/0
Extra: 015121e92dae7a9ad808aa24c6f2a0bb6c9ab033cc7adf331b97e081e6e2df3e1a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da1e12a681d79ca9794c400a1df46ec1895db88384dc2e7e63fb0088671ba0b2 0.600000000000 1658666 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": 1172745, "vin": [ { "gen": { "height": 1172735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da1e12a681d79ca9794c400a1df46ec1895db88384dc2e7e63fb0088671ba0b2" } } ], "extra": [ 1, 81, 33, 233, 45, 174, 122, 154, 216, 8, 170, 36, 198, 242, 160, 187, 108, 154, 176, 51, 204, 122, 223, 51, 27, 151, 224, 129, 230, 226, 223, 62, 26, 2, 17, 0, 0, 0, 1, 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