Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033c2c238cfb9ec04bea02304ad543e06047529ce33b882a03bd77908259dcfe

Tx prefix hash: 58f0bc956f34ab7f62573e39618aa75ac7885d5aa9a2d758aad98b546e3195f5
Tx public key: 619c71c7d3ece68834d0b114a0d0d2414195ced0a98cb8d6b3a0493777e66034
Timestamp: 1695443599 Timestamp [UCT]: 2023-09-23 04:33:19 Age [y:d:h:m:s]: 01:130:18:24:54
Block: 854170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354492 RingCT/type: yes/0
Extra: 01619c71c7d3ece68834d0b114a0d0d2414195ced0a98cb8d6b3a0493777e6603402110000000133af99f4000000000000000000

1 output(s) for total of 0.907361312000 dcy

stealth address amount amount idx
00: 70eb36ae9bf8f46fbbb0fa20f2fc483187de767d415e0b44e0ec748f26968047 0.907361312000 1308128 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": 854180, "vin": [ { "gen": { "height": 854170 } } ], "vout": [ { "amount": 907361312, "target": { "key": "70eb36ae9bf8f46fbbb0fa20f2fc483187de767d415e0b44e0ec748f26968047" } } ], "extra": [ 1, 97, 156, 113, 199, 211, 236, 230, 136, 52, 208, 177, 20, 160, 208, 210, 65, 65, 149, 206, 208, 169, 140, 184, 214, 179, 160, 73, 55, 119, 230, 96, 52, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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