Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bb3e69147faf4b8119c66b65255743399de663f2a1085fad45399d85bea7864

Tx prefix hash: 6678e4a8f1dd4d9cc06274d131bb396f8a942586c1897a08d0824b4d0e764861
Tx public key: 4ff3e9b7e301673f1d71513779a2b899dd0dd775838a44d3152affa83e927e8e
Timestamp: 1574698270 Timestamp [UCT]: 2019-11-25 16:11:10 Age [y:d:h:m:s]: 05:100:12:09:42
Block: 17260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214444 RingCT/type: yes/0
Extra: 014ff3e9b7e301673f1d71513779a2b899dd0dd775838a44d3152affa83e927e8e021100000001f95225a5000000000000000000

1 output(s) for total of 538.134220726000 dcy

stealth address amount amount idx
00: e298a1959266101c8bfb8827ef4c331b630dca338c6eae66cc8e9aa3621eb801 538.134220726000 24861 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": 17270, "vin": [ { "gen": { "height": 17260 } } ], "vout": [ { "amount": 538134220726, "target": { "key": "e298a1959266101c8bfb8827ef4c331b630dca338c6eae66cc8e9aa3621eb801" } } ], "extra": [ 1, 79, 243, 233, 183, 227, 1, 103, 63, 29, 113, 81, 55, 121, 162, 184, 153, 221, 13, 215, 117, 131, 138, 68, 211, 21, 42, 255, 168, 62, 146, 126, 142, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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