Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9530c5488220fc4176f7072fbb5380f432713399006d19698bcc997550e4d607

Tx prefix hash: d5918859a2f2c8962986117049478f95b576625987ce26362e95d80e84b175a4
Tx public key: 1cb6d5e820f5fb0c8c0ce0c730fdb3e33bcd35f3b9765ab66844662771630302
Timestamp: 1695821894 Timestamp [UCT]: 2023-09-27 13:38:14 Age [y:d:h:m:s]: 01:217:14:30:21
Block: 857305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416600 RingCT/type: yes/0
Extra: 011cb6d5e820f5fb0c8c0ce0c730fdb3e33bcd35f3b9765ab66844662771630302021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.885916309000 dcy

stealth address amount amount idx
00: e10c94310db3be30d92a2cfd501bc9bb8055078f32fc8d3ef5c9d9ee7744ddbb 0.885916309000 1311421 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": 857315, "vin": [ { "gen": { "height": 857305 } } ], "vout": [ { "amount": 885916309, "target": { "key": "e10c94310db3be30d92a2cfd501bc9bb8055078f32fc8d3ef5c9d9ee7744ddbb" } } ], "extra": [ 1, 28, 182, 213, 232, 32, 245, 251, 12, 140, 12, 224, 199, 48, 253, 179, 227, 59, 205, 53, 243, 185, 118, 90, 182, 104, 68, 102, 39, 113, 99, 3, 2, 2, 17, 0, 0, 0, 3, 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