Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb81d3707a46fca277a57c3b4027562fbef03056f7a142aae8c8487d431b930a

Tx prefix hash: c1d7cb7d5c61b46f933ead18a24334be25d3577a109ca904d54ba4b12e68ff90
Tx public key: a1f175776aa9ebe0a2d89481ab51eed45444f7de44db7d722f9ab3b23c46d104
Timestamp: 1643503509 Timestamp [UCT]: 2022-01-30 00:45:09 Age [y:d:h:m:s]: 03:044:03:25:04
Block: 428134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 810739 RingCT/type: yes/0
Extra: 01a1f175776aa9ebe0a2d89481ab51eed45444f7de44db7d722f9ab3b23c46d1040211000000012e6b1fd5000000000000000000

1 output(s) for total of 23.410713059000 dcy

stealth address amount amount idx
00: 1927b78b4737cd3ecf117f9df5af44b8e7cb1093846cba3243955238d3879e1e 23.410713059000 837454 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": 428144, "vin": [ { "gen": { "height": 428134 } } ], "vout": [ { "amount": 23410713059, "target": { "key": "1927b78b4737cd3ecf117f9df5af44b8e7cb1093846cba3243955238d3879e1e" } } ], "extra": [ 1, 161, 241, 117, 119, 106, 169, 235, 224, 162, 216, 148, 129, 171, 81, 238, 212, 84, 68, 247, 222, 68, 219, 125, 114, 47, 154, 179, 178, 60, 70, 209, 4, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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