Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d08a621aee461e0ae0d80710554f7a703054910fd30c0c44a435d6faf71204d4

Tx prefix hash: 0c5c67f83e90244eb4886577b7fea113dcaeeaf9a2323f316b4f15cf81084dfa
Tx public key: fa045494d9e3b7fae282b13c48316bf3d1de9a1ef845820f7066514df3432e9b
Timestamp: 1612998570 Timestamp [UCT]: 2021-02-10 23:09:30 Age [y:d:h:m:s]: 03:316:18:00:49
Block: 196224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985381 RingCT/type: yes/0
Extra: 01fa045494d9e3b7fae282b13c48316bf3d1de9a1ef845820f7066514df3432e9b02110000002cb9b01d0b000000000000000000

1 output(s) for total of 137.357235384000 dcy

stealth address amount amount idx
00: 3a1f6a825870cac80ffd8fddd5092abeae71320d44903433e5eea2ac9ebfdc49 137.357235384000 400402 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": 196234, "vin": [ { "gen": { "height": 196224 } } ], "vout": [ { "amount": 137357235384, "target": { "key": "3a1f6a825870cac80ffd8fddd5092abeae71320d44903433e5eea2ac9ebfdc49" } } ], "extra": [ 1, 250, 4, 84, 148, 217, 227, 183, 250, 226, 130, 177, 60, 72, 49, 107, 243, 209, 222, 154, 30, 248, 69, 130, 15, 112, 102, 81, 77, 243, 67, 46, 155, 2, 17, 0, 0, 0, 44, 185, 176, 29, 11, 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