Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58f4cdd8075f8b24dbf1c7a0e427b2a832a73f42dcd7c240e2563b8d0f891ea

Tx prefix hash: 4a8215e26c21329226a3a87d473033a7e6352621077dbf2e3a0f5705a308ab18
Tx public key: 441f771217d8c220db623e31645c757f8659a10700aba8ee46755979d7b9e95b
Timestamp: 1712519512 Timestamp [UCT]: 2024-04-07 19:51:52 Age [y:d:h:m:s]: 00:343:15:22:44
Block: 995506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245730 RingCT/type: yes/0
Extra: 01441f771217d8c220db623e31645c757f8659a10700aba8ee46755979d7b9e95b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6692c8aa2bb3b26727b18b15d7cefc628ca3366fa7f3b24644e6495dfe124252 0.600000000000 1455916 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": 995516, "vin": [ { "gen": { "height": 995506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6692c8aa2bb3b26727b18b15d7cefc628ca3366fa7f3b24644e6495dfe124252" } } ], "extra": [ 1, 68, 31, 119, 18, 23, 216, 194, 32, 219, 98, 62, 49, 100, 92, 117, 127, 134, 89, 161, 7, 0, 171, 168, 238, 70, 117, 89, 121, 215, 185, 233, 91, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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