Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4331ed714983318555b10f1191058bdc8f78fe7f0cb042a6d4d070153c2f8ca9

Tx prefix hash: 3b4bef725cd0f650301d2af78a0c684dec06f9e8424b25ebebc2d476299428f6
Tx public key: 5af1e1f7875003eb97e510a15ac6fc5cb80c7f6ef49e929fd5ef60c9c1d4aae2
Timestamp: 1708996643 Timestamp [UCT]: 2024-02-27 01:17:23 Age [y:d:h:m:s]: 01:092:01:34:53
Block: 966340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326849 RingCT/type: yes/0
Extra: 015af1e1f7875003eb97e510a15ac6fc5cb80c7f6ef49e929fd5ef60c9c1d4aae202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a7d79a5ed2034bc74a8099513ef754f8d1beed1c757fa3d92f3f2cfe4a715c 0.600000000000 1426097 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": 966350, "vin": [ { "gen": { "height": 966340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a7d79a5ed2034bc74a8099513ef754f8d1beed1c757fa3d92f3f2cfe4a715c" } } ], "extra": [ 1, 90, 241, 225, 247, 135, 80, 3, 235, 151, 229, 16, 161, 90, 198, 252, 92, 184, 12, 127, 110, 244, 158, 146, 159, 213, 239, 96, 201, 193, 212, 170, 226, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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