Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d40380369e62a4b9f3226e0a7d282dc3089396d187a7b2d6abf62196c9f138d

Tx prefix hash: 764d4122aacb381aaf802b5fad2af142cbfa2ad6548cc81fe28649e5352acb9f
Tx public key: 37be6907103e0c194eb4a90e79b360fc62e05cf06087adb3e18c7a41d0669c69
Timestamp: 1728370139 Timestamp [UCT]: 2024-10-08 06:48:59 Age [y:d:h:m:s]: 00:107:15:51:11
Block: 1126959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76906 RingCT/type: yes/0
Extra: 0137be6907103e0c194eb4a90e79b360fc62e05cf06087adb3e18c7a41d0669c69021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f5d1869e7295c8ba5c8b8f44d5ec1e349cef02f247156eb1f3a33721747ff28 0.600000000000 1609758 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": 1126969, "vin": [ { "gen": { "height": 1126959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f5d1869e7295c8ba5c8b8f44d5ec1e349cef02f247156eb1f3a33721747ff28" } } ], "extra": [ 1, 55, 190, 105, 7, 16, 62, 12, 25, 78, 180, 169, 14, 121, 179, 96, 252, 98, 224, 92, 240, 96, 135, 173, 179, 225, 140, 122, 65, 208, 102, 156, 105, 2, 17, 0, 0, 0, 8, 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