Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e43ea4117698e14cf74ba43a477d44e822437694402b924fa6473e21fc0dd6

Tx prefix hash: 490c02203cd8a28b9bf87f74a4ceb800ed6aab8c282a56c63756eeea59770eae
Tx public key: d12dd58c231354f3f40eeb175a927e3ad41656c070f6088e3bba0d9bf2b8f95d
Timestamp: 1674462300 Timestamp [UCT]: 2023-01-23 08:25:00 Age [y:d:h:m:s]: 01:286:17:41:07
Block: 680901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465870 RingCT/type: yes/0
Extra: 01d12dd58c231354f3f40eeb175a927e3ad41656c070f6088e3bba0d9bf2b8f95d021100000001e7ace25d000000000000000000

1 output(s) for total of 3.403237616000 dcy

stealth address amount amount idx
00: 73ebb0fb80a38a12dfec3e415e27fe843841c43f0d82e4003027e8d7ef49c8b5 3.403237616000 1122966 of 0

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": 680911, "vin": [ { "gen": { "height": 680901 } } ], "vout": [ { "amount": 3403237616, "target": { "key": "73ebb0fb80a38a12dfec3e415e27fe843841c43f0d82e4003027e8d7ef49c8b5" } } ], "extra": [ 1, 209, 45, 213, 140, 35, 19, 84, 243, 244, 14, 235, 23, 90, 146, 126, 58, 212, 22, 86, 192, 112, 246, 8, 142, 59, 186, 13, 155, 242, 184, 249, 93, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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