Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be93ce8ca8844d368422955bda953a3e52dc927929079e4069d4f454d061ab2a

Tx prefix hash: 97788845d4ac6f190d074cfa0cee84d1b427ed14fa3b568d68a0688f83a3ddcf
Tx public key: 284a30090437fc8fd180f4971964a4ba534aa0d2d5f90c6c1d5f5d9d87afdd83
Timestamp: 1724401457 Timestamp [UCT]: 2024-08-23 08:24:17 Age [y:d:h:m:s]: 00:226:02:56:05
Block: 1094070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161448 RingCT/type: yes/0
Extra: 01284a30090437fc8fd180f4971964a4ba534aa0d2d5f90c6c1d5f5d9d87afdd83021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e990271d7bdd4597625ef3b270e77b0380507d4dd46d73bac506a4cb0149d67 0.600000000000 1569137 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": 1094080, "vin": [ { "gen": { "height": 1094070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e990271d7bdd4597625ef3b270e77b0380507d4dd46d73bac506a4cb0149d67" } } ], "extra": [ 1, 40, 74, 48, 9, 4, 55, 252, 143, 209, 128, 244, 151, 25, 100, 164, 186, 83, 74, 160, 210, 213, 249, 12, 108, 29, 95, 93, 157, 135, 175, 221, 131, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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