Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 446eaef5374b33be25ca2539cbbe8eba978e209f79c639b9528a0a2d95f51538

Tx prefix hash: 0a553c9408180dc8cc94ce9d1b7be2aad514cfadfb7e9ef455fb6d35f08470da
Tx public key: 5f69785ab3cb24cae7ad85bc19fd260e1d7d2097993722a7f1d85baf9f90bdaa
Timestamp: 1725789100 Timestamp [UCT]: 2024-09-08 09:51:40 Age [y:d:h:m:s]: 00:121:11:07:39
Block: 1105556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86862 RingCT/type: yes/0
Extra: 015f69785ab3cb24cae7ad85bc19fd260e1d7d2097993722a7f1d85baf9f90bdaa02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6fe204b05106491110a3751654fa5d3dc0d57bcbc3111c8f734dd9a743acff 0.600000000000 1582927 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": 1105566, "vin": [ { "gen": { "height": 1105556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6fe204b05106491110a3751654fa5d3dc0d57bcbc3111c8f734dd9a743acff" } } ], "extra": [ 1, 95, 105, 120, 90, 179, 203, 36, 202, 231, 173, 133, 188, 25, 253, 38, 14, 29, 125, 32, 151, 153, 55, 34, 167, 241, 216, 91, 175, 159, 144, 189, 170, 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