Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b00e43a6356fd82e1683d1ee8ba8bac2b62346072dfc2ad8c46914de666d6fc3

Tx prefix hash: 4a7534d2171ccb6a1e465f7f140a7aea4512a31bac71ee90eb843e43bb6d0405
Tx public key: 0e6b65d233c84e55e69807e06e22b50517835623abb25f692a20dfcf5a348b0f
Timestamp: 1736745723 Timestamp [UCT]: 2025-01-13 05:22:03 Age [y:d:h:m:s]: 00:342:00:48:40
Block: 1196241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242014 RingCT/type: yes/0
Extra: 010e6b65d233c84e55e69807e06e22b50517835623abb25f692a20dfcf5a348b0f021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14addaea047aaba7f0b4d50de893c79dd7fb637f9d1e5b489ea7e539729435aa 0.600000000000 1682838 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": 1196251, "vin": [ { "gen": { "height": 1196241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14addaea047aaba7f0b4d50de893c79dd7fb637f9d1e5b489ea7e539729435aa" } } ], "extra": [ 1, 14, 107, 101, 210, 51, 200, 78, 85, 230, 152, 7, 224, 110, 34, 181, 5, 23, 131, 86, 35, 171, 178, 95, 105, 42, 32, 223, 207, 90, 52, 139, 15, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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