Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9ce1ca945014f4f2991c740e5f6f41023346766146c8a729fc2ed40178f7d91

Tx prefix hash: fa059c0c73895a774b822b7462205d078cc0ac8c8c9c7858eb3b07099ad769b5
Tx public key: 5fa4eb9d095948c3b73b00d94840be4f82fbe80c04457673339ef964fc69f8a2
Timestamp: 1650347830 Timestamp [UCT]: 2022-04-19 05:57:10 Age [y:d:h:m:s]: 02:215:19:26:31
Block: 483362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 674136 RingCT/type: yes/0
Extra: 015fa4eb9d095948c3b73b00d94840be4f82fbe80c04457673339ef964fc69f8a2021100000001cb8520c2000000000000000000

1 output(s) for total of 15.361063016000 dcy

stealth address amount amount idx
00: 090be4c7f731cd6e1236a3c0bded46ee226f1fcf52b87ce0ba7c76180faf96b4 15.361063016000 905029 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": 483372, "vin": [ { "gen": { "height": 483362 } } ], "vout": [ { "amount": 15361063016, "target": { "key": "090be4c7f731cd6e1236a3c0bded46ee226f1fcf52b87ce0ba7c76180faf96b4" } } ], "extra": [ 1, 95, 164, 235, 157, 9, 89, 72, 195, 183, 59, 0, 217, 72, 64, 190, 79, 130, 251, 232, 12, 4, 69, 118, 115, 51, 158, 249, 100, 252, 105, 248, 162, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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