Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364461e7dd5dad3e9b88e211a7e9492f9c4572b21eca8bba106ded254aeb549c

Tx prefix hash: 27958c40198b7551d8edf803dc7e4c433f748257a3bb0f8bf5f5efc24b4ee96d
Tx public key: 172d212b38a04b7ca8e9c700d361bcf43b1d815fc521b2c7cc868725fe8d5396
Timestamp: 1735056641 Timestamp [UCT]: 2024-12-24 16:10:41 Age [y:d:h:m:s]: 00:091:02:25:44
Block: 1182273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64884 RingCT/type: yes/0
Extra: 01172d212b38a04b7ca8e9c700d361bcf43b1d815fc521b2c7cc868725fe8d5396021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5134f026810b1fb4d11a87ebcf37463efeacc5847592d962461f3ed867727854 0.600000000000 1668706 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": 1182283, "vin": [ { "gen": { "height": 1182273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5134f026810b1fb4d11a87ebcf37463efeacc5847592d962461f3ed867727854" } } ], "extra": [ 1, 23, 45, 33, 43, 56, 160, 75, 124, 168, 233, 199, 0, 211, 97, 188, 244, 59, 29, 129, 95, 197, 33, 178, 199, 204, 134, 135, 37, 254, 141, 83, 150, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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