Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e964c380cee311555847ff3bbbf1c6b356f708143d7af1bc1b4b56a95815e6

Tx prefix hash: 00c01170d9d99d3481293a52f87f8341fda1a48896d03a3c7791323d8fad2f19
Tx public key: 8b5bc28ca9cf22be761c5043d5bdd363a0a50b7dbc3b582338c04f328b2bbd8a
Timestamp: 1720146264 Timestamp [UCT]: 2024-07-05 02:24:24 Age [y:d:h:m:s]: 00:274:11:37:50
Block: 1058760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196121 RingCT/type: yes/0
Extra: 018b5bc28ca9cf22be761c5043d5bdd363a0a50b7dbc3b582338c04f328b2bbd8a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b7d4af9b5c3b7a3500683be56ccd7f50290c1e97f9a9b4489b3d5df2c6682f 0.600000000000 1529217 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": 1058770, "vin": [ { "gen": { "height": 1058760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b7d4af9b5c3b7a3500683be56ccd7f50290c1e97f9a9b4489b3d5df2c6682f" } } ], "extra": [ 1, 139, 91, 194, 140, 169, 207, 34, 190, 118, 28, 80, 67, 213, 189, 211, 99, 160, 165, 11, 125, 188, 59, 88, 35, 56, 192, 79, 50, 139, 43, 189, 138, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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