Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c16c911bf9903ec602677eb52737956b281f3c0480974dd9b1558acbd173bb42

Tx prefix hash: 7b77ee13c1a3e2b3876b92abc8a4ca4873615b00b70efcd2a1f35272cce8070f
Tx public key: 8a0849216f1162cbcc0b73bcd2534fd5778dd90c53a9b7d5ce14c86d8f44d6a2
Timestamp: 1649654783 Timestamp [UCT]: 2022-04-11 05:26:23 Age [y:d:h:m:s]: 03:037:12:27:53
Block: 477764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 807282 RingCT/type: yes/0
Extra: 018a0849216f1162cbcc0b73bcd2534fd5778dd90c53a9b7d5ce14c86d8f44d6a2021100000003c9067537000000000000000000

1 output(s) for total of 16.031338224000 dcy

stealth address amount amount idx
00: 0a00bfc16f9e9ea9caddac9d5a27c2be8504e689fb96dce6c26e4ae4f884910c 16.031338224000 898455 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": 477774, "vin": [ { "gen": { "height": 477764 } } ], "vout": [ { "amount": 16031338224, "target": { "key": "0a00bfc16f9e9ea9caddac9d5a27c2be8504e689fb96dce6c26e4ae4f884910c" } } ], "extra": [ 1, 138, 8, 73, 33, 111, 17, 98, 203, 204, 11, 115, 188, 210, 83, 79, 213, 119, 141, 217, 12, 83, 169, 183, 213, 206, 20, 200, 109, 143, 68, 214, 162, 2, 17, 0, 0, 0, 3, 201, 6, 117, 55, 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