Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5af7334db7d778a6f250bccb9d5ac2d387ef327aeeec26afe3c95e9ff2aa66b1

Tx prefix hash: 3a4fed1776fa7ca8cef544573c9e0673679c0c4a74751f70646a0b1dd8f1ea48
Tx public key: 01fb4aa9ba08c4d1dc35e54a52016eeb2826ab489cf5644dcf698b4de4930d4c
Timestamp: 1740756844 Timestamp [UCT]: 2025-02-28 15:34:04 Age [y:d:h:m:s]: 00:306:15:50:08
Block: 1229174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216988 RingCT/type: yes/0
Extra: 0101fb4aa9ba08c4d1dc35e54a52016eeb2826ab489cf5644dcf698b4de4930d4c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d00e44c7f5c994578621187e1aed9a38af9e03b2999bd70a6a6867668c7f49e 0.600000000000 1716057 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": 1229184, "vin": [ { "gen": { "height": 1229174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d00e44c7f5c994578621187e1aed9a38af9e03b2999bd70a6a6867668c7f49e" } } ], "extra": [ 1, 1, 251, 74, 169, 186, 8, 196, 209, 220, 53, 229, 74, 82, 1, 110, 235, 40, 38, 171, 72, 156, 245, 100, 77, 207, 105, 139, 77, 228, 147, 13, 76, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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