Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d119372dd8c83373824a64b3db0dbcfe414fe304cad2fd4a08679772ee242f2c

Tx prefix hash: fefc0b5cad8e3374e72215fc777390293b3f564d7dbfcae81b936add89a6d517
Tx public key: 9e49e8754d8ebc36c7f0f094113533e8f9235a952d5635210d972331849e49a0
Timestamp: 1579076752 Timestamp [UCT]: 2020-01-15 08:25:52 Age [y:d:h:m:s]: 05:050:11:13:21
Block: 45910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186254 RingCT/type: yes/0
Extra: 019e49e8754d8ebc36c7f0f094113533e8f9235a952d5635210d972331849e49a0021100000059391a8d0e000000000000000000

1 output(s) for total of 432.396281852000 dcy

stealth address amount amount idx
00: 0ec9fb9d2146572aeb99fb81a82a6ba5c7f83fdaddf325cabd22dae45a0a76da 432.396281852000 84171 of 0

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": 45920, "vin": [ { "gen": { "height": 45910 } } ], "vout": [ { "amount": 432396281852, "target": { "key": "0ec9fb9d2146572aeb99fb81a82a6ba5c7f83fdaddf325cabd22dae45a0a76da" } } ], "extra": [ 1, 158, 73, 232, 117, 77, 142, 188, 54, 199, 240, 240, 148, 17, 53, 51, 232, 249, 35, 90, 149, 45, 86, 53, 33, 13, 151, 35, 49, 132, 158, 73, 160, 2, 17, 0, 0, 0, 89, 57, 26, 141, 14, 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