Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb525b0b947b7419c9b2568bf21dddf0f83104df14b5ded4371b66102e13c181

Tx prefix hash: 0f6496c4efa77da10d27997c86bae573ab0e92e381c5c77ca3207e7fcc1b0525
Tx public key: 544bd0a10f9b8ece9a8e1b1376317fbdfa664092c5e4fa89c02c2c05158ef24b
Timestamp: 1721984835 Timestamp [UCT]: 2024-07-26 09:07:15 Age [y:d:h:m:s]: 00:230:13:29:28
Block: 1074011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164697 RingCT/type: yes/0
Extra: 01544bd0a10f9b8ece9a8e1b1376317fbdfa664092c5e4fa89c02c2c05158ef24b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c37b64ee4a68b4a4eaf2f37d0e086ca5ff9cf6a21032794ef0a7cea01902acb 0.600000000000 1546520 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": 1074021, "vin": [ { "gen": { "height": 1074011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c37b64ee4a68b4a4eaf2f37d0e086ca5ff9cf6a21032794ef0a7cea01902acb" } } ], "extra": [ 1, 84, 75, 208, 161, 15, 155, 142, 206, 154, 142, 27, 19, 118, 49, 127, 189, 250, 102, 64, 146, 197, 228, 250, 137, 192, 44, 44, 5, 21, 142, 242, 75, 2, 17, 0, 0, 0, 4, 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