Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1de5d0b53809cffa0b04e5be39eb5f30fdd8ec5f4ec44470bcbd9b0fe7582e

Tx prefix hash: 3a4d65f303c3954e896a4915a04b7192370c600ba4bbd6ccc7986ac01b45929b
Tx public key: 30aa11ef0b02e737f93bcf9ed5443fe34e8aed6d8b2d0920f24f87e6a3aa5e5e
Timestamp: 1736553072 Timestamp [UCT]: 2025-01-10 23:51:12 Age [y:d:h:m:s]: 00:119:07:30:35
Block: 1194642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85082 RingCT/type: yes/0
Extra: 0130aa11ef0b02e737f93bcf9ed5443fe34e8aed6d8b2d0920f24f87e6a3aa5e5e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6c9fab10c6f30ecbf2113779e6e0b224b88d26322ab485d9de8d2c0bcd2c03e 0.600000000000 1681219 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": 1194652, "vin": [ { "gen": { "height": 1194642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6c9fab10c6f30ecbf2113779e6e0b224b88d26322ab485d9de8d2c0bcd2c03e" } } ], "extra": [ 1, 48, 170, 17, 239, 11, 2, 231, 55, 249, 59, 207, 158, 213, 68, 63, 227, 78, 138, 237, 109, 139, 45, 9, 32, 242, 79, 135, 230, 163, 170, 94, 94, 2, 17, 0, 0, 0, 6, 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