Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32d57e9df3d762facb74851bdd3b162f62c1be8a65518cfed2aab62e8b8406d1

Tx prefix hash: 3ea59876d3d8cd0824f4495fe01b7e15f5d59f13d6e1278a49656b7e8d343274
Tx public key: b814b51be03b0c7b21449bab015fbffedff646e1fff6eedd1cd208ed7a8a8be4
Timestamp: 1728093932 Timestamp [UCT]: 2024-10-05 02:05:32 Age [y:d:h:m:s]: 00:178:21:43:06
Block: 1124657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127653 RingCT/type: yes/0
Extra: 01b814b51be03b0c7b21449bab015fbffedff646e1fff6eedd1cd208ed7a8a8be4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19646ddb9093577914ad9f5eac62556e5417be9c8c4b66053e70d94d187d3374 0.600000000000 1607316 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": 1124667, "vin": [ { "gen": { "height": 1124657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19646ddb9093577914ad9f5eac62556e5417be9c8c4b66053e70d94d187d3374" } } ], "extra": [ 1, 184, 20, 181, 27, 224, 59, 12, 123, 33, 68, 155, 171, 1, 95, 191, 254, 223, 246, 70, 225, 255, 246, 238, 221, 28, 210, 8, 237, 122, 138, 139, 228, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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