Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f16115745c9dd10390a38354a33b867a6b7c465044cc119de6572e961eb61af1

Tx prefix hash: e6eca9b3fcf5575b86fc9d3acc42a1f9ca5504e7796e211b29d58c1479b13914
Tx public key: 929ed58663f3000f4a6e1adb6c15e2aadd3b60aee2f88c2d9fed5c6de793a908
Timestamp: 1754934075 Timestamp [UCT]: 2025-08-11 17:41:15 Age [y:d:h:m:s]: 00:012:01:56:11
Block: 1344964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7939 RingCT/type: yes/0
Extra: 01929ed58663f3000f4a6e1adb6c15e2aadd3b60aee2f88c2d9fed5c6de793a908021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd7ba31b8ecee9a345c69f765040db11bdc0e06386cca62028d4c1bee907a76 0.600000000000 1832853 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": 1344974, "vin": [ { "gen": { "height": 1344964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd7ba31b8ecee9a345c69f765040db11bdc0e06386cca62028d4c1bee907a76" } } ], "extra": [ 1, 146, 158, 213, 134, 99, 243, 0, 15, 74, 110, 26, 219, 108, 21, 226, 170, 221, 59, 96, 174, 226, 248, 140, 45, 159, 237, 92, 109, 231, 147, 169, 8, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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