Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af85231683109d1b3f1cf457a82643a34624bc01f9a9a0f9f8847a0717fd08f1

Tx prefix hash: 989e958dd2be2dc7ceb8d3b1fc414e5a87fd5e2058632e89f6b109c7de8443a7
Tx public key: 675fd7a6934aac024bf3d83a0eb5e58a8079ea3c7f883bfe40cc80b234975bef
Timestamp: 1702765400 Timestamp [UCT]: 2023-12-16 22:23:20 Age [y:d:h:m:s]: 01:330:15:28:57
Block: 914669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495167 RingCT/type: yes/0
Extra: 01675fd7a6934aac024bf3d83a0eb5e58a8079ea3c7f883bfe40cc80b234975bef021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99f79a0635c896d60cb29b87bd84d5fab917adce625d11a1a41d3a052be885aa 0.600000000000 1372019 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": 914679, "vin": [ { "gen": { "height": 914669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99f79a0635c896d60cb29b87bd84d5fab917adce625d11a1a41d3a052be885aa" } } ], "extra": [ 1, 103, 95, 215, 166, 147, 74, 172, 2, 75, 243, 216, 58, 14, 181, 229, 138, 128, 121, 234, 60, 127, 136, 59, 254, 64, 204, 128, 178, 52, 151, 91, 239, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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