Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88b6890c7fe9379bd6f5771a86a6fd6dddeb46290198018f005b985eeb4a837a

Tx prefix hash: f0778a6c9430ffffd5f7a5bf381ad237ff6b1035b7167a23c4b36980a739b7d8
Tx public key: 63e01c7ad1e2494b0bdae5f740750e4526a5f8920ef35baa8cfc5c4f64d1379a
Timestamp: 1636577757 Timestamp [UCT]: 2021-11-10 20:55:57 Age [y:d:h:m:s]: 03:123:11:23:18
Block: 371641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 866640 RingCT/type: yes/0
Extra: 0163e01c7ad1e2494b0bdae5f740750e4526a5f8920ef35baa8cfc5c4f64d1379a02110000000106faf294000000000000000000

1 output(s) for total of 36.025256217000 dcy

stealth address amount amount idx
00: e35a1f65a4715c0efd2c09c3b564f83b2c5bdfdcc7f430f0d24dae95fd824e79 36.025256217000 753067 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": 371651, "vin": [ { "gen": { "height": 371641 } } ], "vout": [ { "amount": 36025256217, "target": { "key": "e35a1f65a4715c0efd2c09c3b564f83b2c5bdfdcc7f430f0d24dae95fd824e79" } } ], "extra": [ 1, 99, 224, 28, 122, 209, 226, 73, 75, 11, 218, 229, 247, 64, 117, 14, 69, 38, 165, 248, 146, 14, 243, 91, 170, 140, 252, 92, 79, 100, 209, 55, 154, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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