Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aab8382b6b27ff9162d57736943c4ae427e6f05da46f6ed1a460a39b43815862

Tx prefix hash: 8291da60cefef75ff6208c04e622bbde2290597dc1f1ec815eb20444e9e3557e
Tx public key: 7b95530080d87bfa5ea47f6d0ba1048e589429a0a283520b1d9996d0621b8dc8
Timestamp: 1743107346 Timestamp [UCT]: 2025-03-27 20:29:06 Age [y:d:h:m:s]: 00:239:03:33:56
Block: 1248626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168669 RingCT/type: yes/0
Extra: 017b95530080d87bfa5ea47f6d0ba1048e589429a0a283520b1d9996d0621b8dc8021100000003165b77a1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f00b2b89d335c6be0fb836627f624d33e46df751ef991114d988e81c41a7bce7 0.600000000000 1735659 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": 1248636, "vin": [ { "gen": { "height": 1248626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f00b2b89d335c6be0fb836627f624d33e46df751ef991114d988e81c41a7bce7" } } ], "extra": [ 1, 123, 149, 83, 0, 128, 216, 123, 250, 94, 164, 127, 109, 11, 161, 4, 142, 88, 148, 41, 160, 162, 131, 82, 11, 29, 153, 150, 208, 98, 27, 141, 200, 2, 17, 0, 0, 0, 3, 22, 91, 119, 161, 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