Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27970bd3c02ca5ea4c818caad1633e43fd7a6b9ef0437d0208838abe46dfe8b5

Tx prefix hash: b278485de5afdac4d836e5086e5be26e1db0d540168c1df21f174dbaf661be3a
Tx public key: a0b5d34c7d2f119b3fb8fc0a68ab86815207cae9c655ff13b45d86aef1d9023f
Timestamp: 1761379420 Timestamp [UCT]: 2025-10-25 08:03:40 Age [y:d:h:m:s]: 00:015:11:37:13
Block: 1397507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11076 RingCT/type: yes/0
Extra: 01a0b5d34c7d2f119b3fb8fc0a68ab86815207cae9c655ff13b45d86aef1d9023f0211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248aec1a8ff5c89bbfa7d591751f78a2411e330b4374afd7c46cc197bbacc62b 0.600000000000 1885798 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": 1397517, "vin": [ { "gen": { "height": 1397507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248aec1a8ff5c89bbfa7d591751f78a2411e330b4374afd7c46cc197bbacc62b" } } ], "extra": [ 1, 160, 181, 211, 76, 125, 47, 17, 155, 63, 184, 252, 10, 104, 171, 134, 129, 82, 7, 202, 233, 198, 85, 255, 19, 180, 93, 134, 174, 241, 217, 2, 63, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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