Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c2d0453d6259a1499df5bc09c635cb8c67ad4bb65dd03c361803c5c1d8bd8d

Tx prefix hash: 9eae27632b37822494eb518f228190f13b881a1c9571748487fc7f6184f3a413
Tx public key: 98fc8dbc76aa9a9a5da7bcdaea1859993bb8fd7bd4f4139214488c28d1720bdb
Timestamp: 1724117334 Timestamp [UCT]: 2024-08-20 01:28:54 Age [y:d:h:m:s]: 00:295:03:59:23
Block: 1091694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210851 RingCT/type: yes/0
Extra: 0198fc8dbc76aa9a9a5da7bcdaea1859993bb8fd7bd4f4139214488c28d1720bdb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 775bf02ce4ecd1fbecea673600f9aae0565754fb3ebaad17a1703d83d2a348f5 0.600000000000 1566327 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": 1091704, "vin": [ { "gen": { "height": 1091694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "775bf02ce4ecd1fbecea673600f9aae0565754fb3ebaad17a1703d83d2a348f5" } } ], "extra": [ 1, 152, 252, 141, 188, 118, 170, 154, 154, 93, 167, 188, 218, 234, 24, 89, 153, 59, 184, 253, 123, 212, 244, 19, 146, 20, 72, 140, 40, 209, 114, 11, 219, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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