Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7b170871ba5526fc73d4322b1e478adc3eccd6b2ab0290a3fd11f33ea797d24

Tx prefix hash: 7e65ef1329274ac1a2287ce8b27dc6fda1ea68c8099cf0f8753a7c0f50df1b92
Tx public key: d87e93e592d165cbf9292cec8303953af1e255eab0264ea9d253ea9f5af28d10
Timestamp: 1735393393 Timestamp [UCT]: 2024-12-28 13:43:13 Age [y:d:h:m:s]: 00:078:16:20:51
Block: 1185036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56036 RingCT/type: yes/0
Extra: 01d87e93e592d165cbf9292cec8303953af1e255eab0264ea9d253ea9f5af28d100211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6eb97aef93ba5ea212006c0c626bed96ddf9eee7277984848e301243daa525 0.600000000000 1671501 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": 1185046, "vin": [ { "gen": { "height": 1185036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6eb97aef93ba5ea212006c0c626bed96ddf9eee7277984848e301243daa525" } } ], "extra": [ 1, 216, 126, 147, 229, 146, 209, 101, 203, 249, 41, 44, 236, 131, 3, 149, 58, 241, 226, 85, 234, 176, 38, 78, 169, 210, 83, 234, 159, 90, 242, 141, 16, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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