Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e298f9bc28aeeccb703ef8173141363b19edd82d9ba0ce7db666ab1d36dfa67b

Tx prefix hash: b33e7ed365fa748a22c195bc598f2f2012b7601e65d3fed1bc98179e55b8b7a8
Tx public key: 2ec2db469c6ae15aa2fad55b4e728a5cf4bb0d6e9894a14afacb9f133e25c133
Timestamp: 1737083192 Timestamp [UCT]: 2025-01-17 03:06:32 Age [y:d:h:m:s]: 00:307:04:54:57
Block: 1199029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217077 RingCT/type: yes/0
Extra: 012ec2db469c6ae15aa2fad55b4e728a5cf4bb0d6e9894a14afacb9f133e25c133021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf90cb978723bd71f2c9d4066003ba5ac4614d8d6ae14ef16862ae64e85ba859 0.600000000000 1685658 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": 1199039, "vin": [ { "gen": { "height": 1199029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf90cb978723bd71f2c9d4066003ba5ac4614d8d6ae14ef16862ae64e85ba859" } } ], "extra": [ 1, 46, 194, 219, 70, 156, 106, 225, 90, 162, 250, 213, 91, 78, 114, 138, 92, 244, 187, 13, 110, 152, 148, 161, 74, 250, 203, 159, 19, 62, 37, 193, 51, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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