Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7f96e1e1e33e1a46cabb035d16e88e3a1391d5dddc84bc167946e6269edb6a

Tx prefix hash: 1d4c4fe74ee99176d2d3514b6967e2cfb1a1ace04c0f41ce1a4590fd10d6ddd9
Tx public key: 1274ddc5ef9acab62a6ffd096a118b90ac1c11a5066de2b22a8f44543566e85a
Timestamp: 1574556428 Timestamp [UCT]: 2019-11-24 00:47:08 Age [y:d:h:m:s]: 05:036:17:32:04
Block: 16046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1169132 RingCT/type: yes/0
Extra: 011274ddc5ef9acab62a6ffd096a118b90ac1c11a5066de2b22a8f44543566e85a021100000009f95225a5000000000000000000

1 output(s) for total of 543.042504516000 dcy

stealth address amount amount idx
00: 4453ba8e0e4ca8d2e8f0bd811b54f232858cecfb860ca71bc310ba4408a124a9 543.042504516000 22128 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": 16056, "vin": [ { "gen": { "height": 16046 } } ], "vout": [ { "amount": 543042504516, "target": { "key": "4453ba8e0e4ca8d2e8f0bd811b54f232858cecfb860ca71bc310ba4408a124a9" } } ], "extra": [ 1, 18, 116, 221, 197, 239, 154, 202, 182, 42, 111, 253, 9, 106, 17, 139, 144, 172, 28, 17, 165, 6, 109, 226, 178, 42, 143, 68, 84, 53, 102, 232, 90, 2, 17, 0, 0, 0, 9, 249, 82, 37, 165, 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