Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31664dfa487718fcd019fb196921510e3fe17067e7224e2e86497fe396b3d7a5

Tx prefix hash: b9dd42f7934518eee8a8a9cda70456c8afc4b75acaf20662c3059db5023e9a26
Tx public key: 3a5dcd92c1e48584a4806b025ce8896a24b1096ffb977f3cc1f1068c2fe956ad
Timestamp: 1746985971 Timestamp [UCT]: 2025-05-11 17:52:51 Age [y:d:h:m:s]: 00:184:08:32:57
Block: 1280753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129459 RingCT/type: yes/0
Extra: 013a5dcd92c1e48584a4806b025ce8896a24b1096ffb977f3cc1f1068c2fe956ad0211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 159aa958e8155e7b2bd923cb025ec9cc23f7b90ef1ddfdd3debbe1a91fe2f4dc 0.600000000000 1768144 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": 1280763, "vin": [ { "gen": { "height": 1280753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "159aa958e8155e7b2bd923cb025ec9cc23f7b90ef1ddfdd3debbe1a91fe2f4dc" } } ], "extra": [ 1, 58, 93, 205, 146, 193, 228, 133, 132, 164, 128, 107, 2, 92, 232, 137, 106, 36, 177, 9, 111, 251, 151, 127, 60, 193, 241, 6, 140, 47, 233, 86, 173, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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