Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b405616b7ae1834fdd3e4c9195c1ec4b0c19269528679175d8e4567ddccebf

Tx prefix hash: 7acf77fc8539028638e56f25c302090eca505d1c1db36b970be0c2c82fdee44d
Tx public key: 98d3a492f6da76cff9941e92b9137e2b16411ef44c27cde9950445e86a2e4ea6
Timestamp: 1709265298 Timestamp [UCT]: 2024-03-01 03:54:58 Age [y:d:h:m:s]: 01:040:03:23:26
Block: 968567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289700 RingCT/type: yes/0
Extra: 0198d3a492f6da76cff9941e92b9137e2b16411ef44c27cde9950445e86a2e4ea602110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d831c623284db1e4332b522dd6ba1ede3f70693e897202c6697fcc4f08b4436 0.600000000000 1428384 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": 968577, "vin": [ { "gen": { "height": 968567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d831c623284db1e4332b522dd6ba1ede3f70693e897202c6697fcc4f08b4436" } } ], "extra": [ 1, 152, 211, 164, 146, 246, 218, 118, 207, 249, 148, 30, 146, 185, 19, 126, 43, 22, 65, 30, 244, 76, 39, 205, 233, 149, 4, 69, 232, 106, 46, 78, 166, 2, 17, 0, 0, 0, 14, 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