Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc5fd7c19b016bf0da09cfbec223be6b75e6ba4c5ee54ee111392429a713d0f7

Tx prefix hash: 14f95795b5d9d091abc3b263db85f421a19c934e6feed468dbc70a4e50a98818
Tx public key: 472ccf87c968f2a324b7413a18f8c23794a8bcef4c25b26471be09f49f07ccef
Timestamp: 1724908530 Timestamp [UCT]: 2024-08-29 05:15:30 Age [y:d:h:m:s]: 00:334:19:01:28
Block: 1098243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238042 RingCT/type: yes/0
Extra: 01472ccf87c968f2a324b7413a18f8c23794a8bcef4c25b26471be09f49f07ccef02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19f81b43afadf5151523f68a92d5f1465ba05e1ae0af69a8adea6367798a9118 0.600000000000 1573894 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": 1098253, "vin": [ { "gen": { "height": 1098243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19f81b43afadf5151523f68a92d5f1465ba05e1ae0af69a8adea6367798a9118" } } ], "extra": [ 1, 71, 44, 207, 135, 201, 104, 242, 163, 36, 183, 65, 58, 24, 248, 194, 55, 148, 168, 188, 239, 76, 37, 178, 100, 113, 190, 9, 244, 159, 7, 204, 239, 2, 17, 0, 0, 0, 5, 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