Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea2613f26e76048e46072c137434451d61974eaff13f68c1b7f1d587509d6b49

Tx prefix hash: 9ad76ea7e64fd1e4273157c1c0f9cf290ba302f2bee9dbcbb080a159b281f368
Tx public key: 66a5090eaf634f9091af36958b65db2dc2c46e9703787e4a2477d51e6d65f516
Timestamp: 1702315144 Timestamp [UCT]: 2023-12-11 17:19:04 Age [y:d:h:m:s]: 01:120:04:58:59
Block: 910944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347043 RingCT/type: yes/0
Extra: 0166a5090eaf634f9091af36958b65db2dc2c46e9703787e4a2477d51e6d65f51602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd5edfe3ca935f3506e60f4e6561515fdc959a3d2bb67c2b761bc646329f17e1 0.600000000000 1368119 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": 910954, "vin": [ { "gen": { "height": 910944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd5edfe3ca935f3506e60f4e6561515fdc959a3d2bb67c2b761bc646329f17e1" } } ], "extra": [ 1, 102, 165, 9, 14, 175, 99, 79, 144, 145, 175, 54, 149, 139, 101, 219, 45, 194, 196, 110, 151, 3, 120, 126, 74, 36, 119, 213, 30, 109, 101, 245, 22, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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