Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0fc23d9c1bf0ee5ffdde5e7d5b1859574bb4ae4424304bfa84c4523cac9da20

Tx prefix hash: 14849defc381568c2798c3ced08d9e4f36c310ed43672f33c35bd30b9fce1c68
Tx public key: f261b6235638c1e985cd31164ffa07bd15df651ab2fd4c8472f6544e3d8c5af8
Timestamp: 1635284110 Timestamp [UCT]: 2021-10-26 21:35:10 Age [y:d:h:m:s]: 03:138:15:19:26
Block: 361106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877313 RingCT/type: yes/0
Extra: 01f261b6235638c1e985cd31164ffa07bd15df651ab2fd4c8472f6544e3d8c5af8021100000001f56b629f000000000000000000

1 output(s) for total of 39.039687003000 dcy

stealth address amount amount idx
00: f79a3aebe71afa554693f3e305f1e73f3f7bb3d21f5ee615b5af40f85639588e 39.039687003000 734783 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": 361116, "vin": [ { "gen": { "height": 361106 } } ], "vout": [ { "amount": 39039687003, "target": { "key": "f79a3aebe71afa554693f3e305f1e73f3f7bb3d21f5ee615b5af40f85639588e" } } ], "extra": [ 1, 242, 97, 182, 35, 86, 56, 193, 233, 133, 205, 49, 22, 79, 250, 7, 189, 21, 223, 101, 26, 178, 253, 76, 132, 114, 246, 84, 78, 61, 140, 90, 248, 2, 17, 0, 0, 0, 1, 245, 107, 98, 159, 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