Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c510d793062c76702be0de444a80619783eedea24a594c1ce2159ac285a69c2f

Tx prefix hash: 3d51109ae249babc4dff56f5ad1fee2aa1ac7f6aea002b5a5b850060c88da960
Tx public key: 3514a2157e10f4f67237e0f2b1065a9b355af2189c74eab9885f01b90093ca6a
Timestamp: 1657687534 Timestamp [UCT]: 2022-07-13 04:45:34 Age [y:d:h:m:s]: 02:216:17:01:49
Block: 542656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 675991 RingCT/type: yes/0
Extra: 013514a2157e10f4f67237e0f2b1065a9b355af2189c74eab9885f01b90093ca6a021100000001cb8520c2000000000000000000

1 output(s) for total of 9.771372010000 dcy

stealth address amount amount idx
00: 8c260c5121767e815ae1e3f85f63ffb32e4743fce8b3b5a183a1ce4331361561 9.771372010000 973241 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": 542666, "vin": [ { "gen": { "height": 542656 } } ], "vout": [ { "amount": 9771372010, "target": { "key": "8c260c5121767e815ae1e3f85f63ffb32e4743fce8b3b5a183a1ce4331361561" } } ], "extra": [ 1, 53, 20, 162, 21, 126, 16, 244, 246, 114, 55, 224, 242, 177, 6, 90, 155, 53, 90, 242, 24, 156, 116, 234, 185, 136, 95, 1, 185, 0, 147, 202, 106, 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