Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e41dfe4231f793b65fad9bfbbcd925fbc67104274760241e37528022bdbf9b1e

Tx prefix hash: 0da0431a849574f4719472981f3c85894531a57fc52f0a6dbdcd2e4b72cb332a
Tx public key: fc3b600450b5f8fdde20bcf9d5236145d87582a0b55addabf3aa3a00da2dc23e
Timestamp: 1695529928 Timestamp [UCT]: 2023-09-24 04:32:08 Age [y:d:h:m:s]: 01:114:22:10:16
Block: 854885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343418 RingCT/type: yes/0
Extra: 01fc3b600450b5f8fdde20bcf9d5236145d87582a0b55addabf3aa3a00da2dc23e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.902425097000 dcy

stealth address amount amount idx
00: 9093d3d4ba93bd8c384e360c592024d49b51f622ba103179206d59c85ad973e9 0.902425097000 1308879 of 0

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": 854895, "vin": [ { "gen": { "height": 854885 } } ], "vout": [ { "amount": 902425097, "target": { "key": "9093d3d4ba93bd8c384e360c592024d49b51f622ba103179206d59c85ad973e9" } } ], "extra": [ 1, 252, 59, 96, 4, 80, 181, 248, 253, 222, 32, 188, 249, 213, 35, 97, 69, 216, 117, 130, 160, 181, 90, 221, 171, 243, 170, 58, 0, 218, 45, 194, 62, 2, 17, 0, 0, 0, 4, 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