Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79d796c526cf593c35a13c832151c65fc19b239bbcf352522f300d7aa7b70bd5

Tx prefix hash: f5557369403603cee2542d53d7d782cfe147c7cb70a34938c245918a076da18a
Tx public key: 1fe00cb147d95cc53895a1c286c00ebb0ea294279b35af42d0909f904178e67d
Timestamp: 1706199200 Timestamp [UCT]: 2024-01-25 16:13:20 Age [y:d:h:m:s]: 00:355:13:01:25
Block: 943116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254545 RingCT/type: yes/0
Extra: 011fe00cb147d95cc53895a1c286c00ebb0ea294279b35af42d0909f904178e67d0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f947db84292314cc017dc7dc99ce7ed2584e9b09e662ea8211dd1b4cc7e748 0.600000000000 1401316 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": 943126, "vin": [ { "gen": { "height": 943116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f947db84292314cc017dc7dc99ce7ed2584e9b09e662ea8211dd1b4cc7e748" } } ], "extra": [ 1, 31, 224, 12, 177, 71, 217, 92, 197, 56, 149, 161, 194, 134, 192, 14, 187, 14, 162, 148, 39, 155, 53, 175, 66, 208, 144, 159, 144, 65, 120, 230, 125, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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